Installation guide for PASCAL and PASSGO, as distributed by STANFORD LOTS,
for release 1.1, 6-sep-79.

Take the next files and load them in the corresponding directories:

1. SYS:PASCAL.EXE	The Pascal Compiler
2. SYS:PASSGO.EXE	The Passgo (Incore, Load-and-go) compiler
3. SYS:PCREF.EXE	The cross-referencer, reporter
				of statement counts.
4. SYS:PFORM.EXE	The prettyprinter.
5. SYS:PASLIB.REL	The runtime Library.
6. HLP:PASCAL.HLP	a HELP file for PASCAL and PASSGO.
7. HLP:PCREF.HLP	a HELP file for PCREF.
8. HLP:PFORM.HLP	a HELP file for PFORM.
9. DOC:PASCAL.MAN	a Manual for this implementation, asuming you
				know Wirth's report on PASCAL.
10. DOC:PASCAL.DOC	data on some of the internals of PASCAL.
11. PAS:PASCAL.PAS	The source for both PASCAL and PASSGO.
12. PAS:PCREF.PAS	The source for the cross-referencer.
13. PAS:PFORM.PAS	The source for the prettyprinter.
14. PAS:LIBPAS.PAS	Part of the runtimes.
15. PAS:LIBMAC.MAC	The rest of the runtimes.
16. PAS:PASLIB.LST	A cross-reference of entry points in PASLIB.
17. DOC:PASCAL.CHANGES	A brief story of the most relevant differences
				between this compiler and the Hamburg
				PASCAL, distributed by DECUS, version 1976.

The other files (.REL) are there to help you in case you have any
	problem running the EXECs. The first pages of the source
	of the compiler (PAS:PASCAL.PAS) have an explanation on 
	how to use them.

There is one file that can help you to find out if the interface with
	COMP and the EXEC is proper: CCL.REL; if loaded with the compiler,
	it will show the contents of the .TMP or TMPCOR file as it is 
	read. To use it:
		@RENAME PASCAL.EXE PASCAL.GOOD
		@LOAD PASCAL,CCL
		@SAVE PASCAL
	Don't put this	as the official version.

If you have one of our previous versions, you have PCROSS, which does
	the same as PCREF and PFORM put together. (in fact, the two
	sources came out of PCROSS). For you, and for this time only,
	we are including a PCROSS program that limits itself to say
	'I do not exist anymore. Please try PCREF and PFORM'. If you
	don't need this program, better.

The one file that has not been mentioned is COPY.PAS: this is a sample
	Pascal program, so that you can test the compiler with
	something small. It makes an identical copy of the input file,
	except that it comes out in all upper case. (PASCAL programs
	supported by this implementation are case blind.)

Once you are installed, you will want to change the HEADER in page
	3 of the compilers, to give your installation name, instead
	of LOTS. Remember to change also the length, in the next line.

NOTE on compatibility: This version is upwards compatible with previous
	versions of PASCAL/PASSGO, except for the definition of the
	runtime procedure ASKFILENAME. However, the source of the
	compiler cannot be compiled by previous versions.If you cannot
	use the .EXE files, just build your own by using the .REL files.

This compiler is distributed on an 'as is' basis, so it is not guaranteed.
	However, it is extensively used at Stanford University, and I
	personally use it all the time, so whenever a bug is found, I 
	am the first one interested on getting it fixed. Should you 
	have any problems, or FIX any bugs, please notify me.

Things that you can expect in future releases, besides fixing bugs and
	improving the documentation:
	   - Time monitoring feature.
	   - PCREF (and PSTAT coming) taking good advantage of the
		information provided by the /PROFILE and /MONITOR switches.
	   - PASCAL, PCREF and PFORM being able to keep the case of the
		original source, for output purposes.
	   - 20-native version.
	   - A nicer, more friendly user interfase (Input error in a ter-
		minal will not blow the run, but reprompt you)
	All these features are in process now. Some are already in the
	test fase.

Wish list: (Things that we WANT to do, but we just don't have the time
	to do them)
	   - Make the debugger more reliable, and reduce its overhead.
	   - Add features to it.
	   - Sets of any size (probably 4-word sets first).
	   - Type char extended up to '⎇'.
	   - constant expressions evaluated at compile time.
	   - some other simple optimization techniques, that could be
		done in one pass (not many left: the original Hamburg
		version is GOOD at this)
	   - make the heap a REAL heap, not a stack.
	   - add more utility programs (mixture editor-prettyprinter,
		or better yet, something like MENTOR?)
	   - flag the use of nonstandard and/or nontransportable features.
	   - and many, many more.

If you want to add to the wish list, or to help us making it a reality,
	please contact me (Armando).

For distribution related matters, please contact J.Q. Johnson at LOTS:
	(415)497-1792, or LOTS Computer Facility
			  Stanford, CA 94305
	Admin.JQJ@SU-SCORE, JQJ@SU-AI

For anything related to the compiler, the cross-referencer, the manuals,
	ideas, complaints, comments, etc., please contact me:
		   Armando R. Rodriguez		(415)497-4971
		or LOTS Computer Facility
		   Stanford, CA 94305
	ARR@SU-AI, CSL.ARMANDO@SU-SCORE